[Prism] Fix process timeouts between highlight calls for long building pages #138
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In case a page takes time to build and contains multiple highlight calls, the time elapsed between 2 calls might be too long and the process timeout.
ogizanagi
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In case a page takes time to build and contains multiple highlight calls,
the time elapsed between 2 calls might be too long and the process might timeout (for instance, if there is a large amount of images to resize in the page).
Instead of using a global timeout for the process, let's use an idle timeout (time without any output) between each highlight call and reset it after getting a response from the Node process.